home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / p_man / cat3 / Xm / XmDeactivateProtocol.z / XmDeactivateProtocol
Text File  |  1998-10-30  |  4KB  |  67 lines
  1.  
  2.  
  3.  
  4.      XXXXmmmmDDDDeeeeaaaaccccttttiiiivvvvaaaatttteeeePPPPrrrroooottttooooccccoooollll((((3333XXXX))))  UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV  XXXXmmmmDDDDeeeeaaaaccccttttiiiivvvvaaaatttteeeePPPPrrrroooottttooooccccoooollll((((3333XXXX))))
  5.  
  6.  
  7.  
  8.      NNNNAAAAMMMMEEEE
  9.           XXXXmmmmDDDDeeeeaaaaccccttttiiiivvvvaaaatttteeeePPPPrrrroooottttooooccccoooollll - A VendorShell function that
  10.           deactivates a protocol without removing it
  11.  
  12.      SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  13.           #include <Xm/Xm.h>
  14.           #include <Xm/Protocols.h>
  15.           vvvvooooiiiidddd XXXXmmmmDDDDeeeeaaaaccccttttiiiivvvvaaaatttteeeePPPPrrrroooottttooooccccoooollll(
  16.           WWWWiiiiddddggggeeeetttt sssshhhheeeellllllll,
  17.           AAAAttttoooommmm pppprrrrooooppppeeeerrrrttttyyyy,
  18.           AAAAttttoooommmm pppprrrroooottttooooccccoooollll);
  19.  
  20.      VVVVEEEERRRRSSSSIIIIOOOONNNN
  21.           This page documents Motif 2.1.
  22.  
  23.      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  24.           XXXXmmmmDDDDeeeeaaaaccccttttiiiivvvvaaaatttteeeePPPPrrrroooottttooooccccoooollll deactivates a protocol without removing
  25.           it.  It updates the handlers and the _p_r_o_p_e_r_t_y if the _s_h_e_l_l
  26.           is realized. It is sometimes useful to allow a protocol's
  27.           state information (callback lists, and so on) to persist,
  28.           even though the client may choose to temporarily resign from
  29.           the interaction.  The main use of this capability is to
  30.           gray/ungray ffff....sssseeeennnndddd____mmmmssssggggentries in the MWM system menu.  To
  31.           support this capability, _p_r_o_t_o_c_o_l is allowed to be in one of
  32.           two states: active or inactive.  If _p_r_o_t_o_c_o_l is active and
  33.           _s_h_e_l_l is realized, _p_r_o_p_e_r_t_y contains the _p_r_o_t_o_c_o_l AAAAttttoooommmm.  If
  34.           _p_r_o_t_o_c_o_l is inactive, AAAAttttoooommmm is not present in the _p_r_o_p_e_r_t_y.
  35.  
  36.           XXXXmmmmDDDDeeeeaaaaccccttttiiiivvvvaaaatttteeeeWWWWMMMMPPPPrrrroooottttooooccccoooollll is a convenience interface.  It calls
  37.           XXXXmmmmDDDDeeeeaaaaccccttttiiiivvvvaaaatttteeeePPPPrrrroooottttooooccccoooollllwith the property value set to the atom
  38.           returned by interning WWWWMMMM____PPPPRRRROOOOTTTTOOOOCCCCOOOOLLLLSSSS.
  39.  
  40.           _s_h_e_l_l     Specifies the widget with which the protocol
  41.                     property is associated
  42.  
  43.           _p_r_o_p_e_r_t_y  Specifies the protocol property
  44.  
  45.           _p_r_o_t_o_c_o_l  Specifies the protocol atom
  46.  
  47.           For a complete definition of VendorShell and its associated
  48.           resources, see VVVVeeeennnnddddoooorrrrSSSShhhheeeellllllll(3).
  49.  
  50.      RRRREEEELLLLAAAATTTTEEEEDDDD
  51.           mmmmwwwwmmmm(1), VVVVeeeennnnddddoooorrrrSSSShhhheeeellllllll(3), XXXXmmmmAAAAccccttttiiiivvvvaaaatttteeeePPPPrrrroooottttooooccccoooollll(3),
  52.           XXXXmmmmDDDDeeeeaaaaccccttttiiiivvvvaaaatttteeeeWWWWMMMMPPPPrrrroooottttooooccccoooollll(3), and XXXXmmmmIIIInnnntttteeeerrrrnnnnAAAAttttoooommmm(3).
  53.  
  54.  
  55.  
  56.  
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.      Page 1                                         (printed 10/24/98)
  64.  
  65.  
  66.  
  67.